You can use a number of command to verify the configuration of your feature, service, or system. Many are hierarchical in their implementation and some are specific to portions of or specific lines in the configuration file.
In many configurations, specific features are set and need to be verified. Examples include APN and IP address pool configuration. Using these examples, enter the following commands to verify proper feature configuration:
The output displays the complete configuration for the APN. In this example, an APN called apn1 is configured.
The output from this command should look similar to the sample shown below. In this example, all IP pools were configured in the isp1 context.
PG00 ipsec 12.12.12.0 255.255.255.0 0 254
PG00 pool1 10.10.0.0 255.255.0.0 0 65534
SG00 vpnpool 192.168.1.250 192.168.1.254 0 5
IMPORTANT: Many features can be configured on the system. There are show commands specifically for these features. Refer to the Command Line Interface Reference for more information.The output is a concise listing of the service parameter settings similar to the sample displayed below. In this example, a P-GW service called pgw1 is configured.
show context name <name>
The output shows the active context. Its ID is similar to the sample displayed below. In this example, a context named test1 is configured.
Verify that your entire configuration file was created and configured properly by entering the following command:
This command displays the entire configuration including the context and service configurations defined above.
This command displays errors it finds within the configuration. For example, if you have created a service named “service1”, but entered it as “srv1” in another part of the configuration, the system displays this error.
You must refine this command to specify particular sections of the configuration. Add the section keyword and choose a section from the help menu:
Save system configuration information to a file locally or to a remote node on the network. You can use this configuration file on any other systems that require the same configuration.
Files that you save locally can be stored in the SPC’s/SMC’s CompactFlash or on an installed PCMCIA memory card on the SPC/SMC. Files that you save to a remote network node can be transmitted via FTP or TFTP.
[local]host_name#
|
Specifies the path and name to which the configuration file is to be stored. url may refer to a local or a remote file. url must be entered using one of the following formats:
/flash corresponds to the CompactFlash on the SPC/SMC.
/pcmcia1 corresponds to PCMCIA slot 1.
/pcmcia2 corresponds to PCMCIA slot 2.
ipaddr is the IP address of the network server.
host_name is the network server’s hostname.
port# is the network server’s logical port number. Defaults are:
Note: host_name can only be used if the networkconfig parameter is configured for DHCP and the DHCP server returns a valid nameserver.dx
username is the username required to gain access to the server, if necessary.
pwd is the password for the specified username if required.
/dir specifies the directory where the file is located if one exists.
/file_name specifies the name of the configuration file to be saved.
Note: Name configuration files with a .cfg extension.
|
|||||||||||
|
-redundant
|
Optional: This keyword directs the system to save the CLI configuration file to the local device, defined by the url variable, and then automatically copies the file to the like device on the standby SPC/SMC, if available.
Note: This keyword works only for like local devices that are located on both the active and standby SPCs/SMCs. For example, if you save the file to the /pcmcia1 device on the active SPC/SMC, that same type of device (a PC-Card in Slot 1 of the standby SPC/SMC) must be available. Otherwise, a failure message is displayed.
Note: If saving the file to an external network (non-local) device, the system disregards this keyword.
|
||||||||||
|
Optional: Indicates that no confirmation is to be given prior to saving the configuration information to the specified filename (if one was specified) or to the currently active configuration file (if none was specified).
|
|||||||||||
|
Optional: This keyword causes the CLI configuration file to be saved with all passwords in plain text, rather than their default encrypted format.
|
|||||||||||
|
Optional: Specifies to display every parameter that is being saved to the new configuration file.
|
IMPORTANT: The -redundant keyword is only applicable when saving a configuration file to local devices.This command does not synchronize the local file system. If you have added, modified, or deleted other files or directories to or from a local device for the active SPC/SMC, then you must synchronize the local file system on both SPCs/SMCs.
To save a configuration file called system.cfg to a directory that was previously created called cfgfiles on the SPC’s/SMC’s CompactFlash, enter the following command:
save configuration /flash/cfgfiles/system.cfg
To save a configuration file called simple_ip.cfg to a directory called host_name_configs using an FTP server with an IP address of 192.168.34.156 on which you have an account with a username of administrator and a password of secure, use the following command:
To save a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command:
